Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1033

reference: 180-tree-1
name: 1033
tree-preservation-order: undefined
180-tpo-1
uprn
address-text
point: POINT (-0.938549 50.858830)
geometry: MULTIPOLYGON (((-0.938493 50.858824,-0.938495 50.858835,-0.938503 50.858845,-0.938515 50.858853,-0.938531 50.858858,-0.938549 50.858860,-0.938566 50.858858,-0.938582 50.858853,-0.938595 50.858846,-0.938603 50.858836,-0.938606 50.858825,-0.938604 50.858813,-0.938596 50.858803,-0.938583 50.858795,-0.938568 50.858790,-0.938550 50.858788,-0.938533 50.858790,-0.938517 50.858795,-0.938504 50.858803,-0.938496 50.858812,-0.938493 50.858824)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL